Managing notifications pushed to user devices

ABSTRACT

In one embodiment, a first computing device determines whether one or more conditions are satisfied for not pushing communications to a second computing device associated with a user; and if the one or more conditions are satisfied, then refrains from pushing any communication to the second computing device.

TECHNICAL FIELD

This disclosure generally relates to transmitting data between twoelectronic devices and more specifically relates to managingcommunication connections between a server and a client and transmittingdata between the server and the client over the communicationconnections.

BACKGROUND

When two electronic devices are connected to a network (e.g., a computeror communication network), data may be transmitted between the twodevices over the network using one or more suitable network protocols.For example, in a client-server environment, data may be transmittedbetween a server and a client over a network to which both the serverand the client are connected. Of course, a network may include anynumber of sub-networks. By transmitting data between the two devices,the two devices may communicate with each other.

In network communications, there are two ways to send a communicationfrom one device to another device: push and pull. With push technology,the request for the communication transaction is initiated by thesending device. That is, the sending device “pushes” the communication,so to speak, to the receiving device. In this case, the sending devicemay be considered the active party and the receiving device may beconsidered the passive party in the transaction. In contrast, with pulltechnology, the request for the communication transaction is initiatedby the receiving device. That is, the receiving device “pulls” thecommunication, so to speak, from the sending device. In this case, thesending device may be considered the passive party and the receivingdevice may be considered the active party in the transaction.

SUMMARY

This disclosure generally relates to transmitting data between twoelectronic devices and more specifically relates to managingcommunication connections between a server and a client and transmittingdata between the server and the client over the communicationconnections.

In particular embodiments, a first computing device determines whetherone or more conditions are satisfied for not pushing communications to asecond computing device associated with a user; and if the one or moreconditions are satisfied, then refrains from pushing any communicationto the second computing device. In particular embodiments, theconditions may be determined based on, for example and withoutlimitation, a hardware or a software switch on the second computingdevice, a calendar of the user, the currently location of the secondcomputing device, or the second computing device's proximity to a personor an object.

These and other features, aspects, and advantages of the disclosure aredescribed in more detail below in the detailed description and inconjunction with the following figures.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example client-server environment.

FIG. 2 illustrates an example of pushing a notification to a user'sdevice.

FIG. 3 illustrates an example user device.

FIG. 4 illustrates an example method for turning on or off notificationspushed to a user using a hardware or software switch.

FIG. 5 illustrates an example method that a sensors hub may performcertain tasks.

FIG. 6 illustrates an example connection pool between two devices.

FIG. 7 illustrates an example method for sharing connections in aconnection pool among multiple software applications.

FIG. 8 illustrates an example network environment.

FIG. 9 illustrates an example computer system.

DESCRIPTION OF EXAMPLE EMBODIMENTS

This disclosure is now described in detail with reference to a fewembodiments thereof as illustrated in the accompanying drawings. In thefollowing description, numerous specific details are set forth in orderto provide a thorough understanding of this disclosure. However, thisdisclosure may be practiced without some or all of these specificdetails. In other instances, well known process steps and/or structureshave not been described in detail in order not to unnecessarily obscurethis disclosure. In addition, while the disclosure is described inconjunction with the particular embodiments, it should be understoodthat this description is not intended to limit the disclosure to thedescribed embodiments. To the contrary, the description is intended tocover alternatives, modifications, and equivalents as may be includedwithin the spirit and scope of the disclosure as defined by the appendedclaims.

In network communications, one device may “push” a communication toanother device. In particular embodiments, with push technology, thesending device typically initiates the communication transaction and maytransmit the communication to the receiving device without obtaining apermission from the receiving device first. In other words, thecommunication is “pushed” to the receiving device whether or not thereceiving device actually wants to receive the communication.

Push technology may be used under various circumstances. For example, ina client-server environment, a server may push communications to aclient. The client may be any type of electronic device capable ofnetwork communications. In particular embodiments, the client may be amobile device (e.g., a mobile telephone, a smart phone, a tabletcomputer, etc.) capable of wireless communications, and the server maypush communications, sent over a mobile network or a wireless network,to the mobile client. Alternatively or in addition, in particularembodiments, the client may be a non-mobile computing device (e.g., adesktop computer) capable of connecting to a computer network through awired connection (e.g., an Ethernet connection). The server may pushcommunications to the non-mobile client over the computer network (e.g.,the Internet).

In particular embodiments, a social-networking system implemented, forexample, as a social-networking website, may push communications to theclient devices of its users. A social network, in general, is a socialstructure made up of entities, such as individuals or organizations,that are connected by one or more types of interdependency orrelationships, such as friendship, kinship, common interest, financialexchange, dislike, or relationships of beliefs, knowledge, or prestige.In more recent years, social networks have taken advantage of theInternet. There are social-networking systems existing on the Internetin the form of social-networking websites. Such social-networkingwebsites enable their members, who are commonly referred to as websiteusers, to perform various social activities. For example, thesocial-networking website operated by Facebook, Inc. at www.facebook.comenables its users to communicate with their friends via emails, instantmessages, or blog postings, organize social events, share photos,receive news of their friends or interesting events, play games, etc.

There are various types of communications that may be pushed to a clientdevice, such as, for example and without limitation, system updatemessages, software update messages, advertisements, alerts, user accountnotices, social-networking messages, service agreement updates, or acombination of different types of communications. This disclosurecontemplates any applicable types of communications. A client device maybe connected to a network via a wireless or wire-line connection usingany suitable communication or network protocol (e.g., TCP/IP). Inparticular embodiments, a communication pushed to a client may bereferred to as a “push notification”. An example push notification is aShort Message Service (SMS) notification. The content of the individualnotifications may vary. Often the content of a notification may concernan entity, which may a human or a non-human entity (e.g., anorganization, a location, a product, a software application, a movie, asubject matter, etc.). A notification may originate from thesocial-networking system (e.g., notifications on social information orsocial connections) or from a third party (e.g., notifications on thethird-party's products or services).

Sometimes, the user devices to which the notifications are pushed may bemobile devices (e.g., mobile telephones or tablet computers). Given therelatively small size of the display of a typical mobile device, thenotifications are often displayed as overlays on the current interfaceview. Some push notifications may be interruptive and some may benon-interruptive. In particular embodiments, an interruptive pushnotification, when pushed to a client, may be presented to the user ofthe client immediately or soon after it is received by the client. Evenif the user is performing other activities with the client, theactivities may be interrupted and suspended by the interruptive pushnotification. The user may need to respond to the interruptive pushnotification first before he/she can continue with performing the otheractivities with the client. For example, suppose that an error alert ispushed to a smart phone (e.g., an iPhone or Blackberry) while the userof the smart phone is checking map directions using Google Maps. If theerror alert is an interruptive notification, then the error alert may bepresented to the user immediately after it is received by the smartphone, and the user may need to respond to the error alert (e.g., push abutton to indicate that the user is aware of the error) before the usermay continue with checking map directions. On the other hand, anon-interruptive push notification, when pushed to a client, may bestored on the client for some period of time before it is presented tothe user of the client. A non-interruptive push notification typicallydoes not require the user's immediate attention. Instead, the user mayrespond to it at leisure (e.g., when the user has time). For example,suppose that a coupon from a coffee house near the current location of auser is pushed to the user's smart phone while the user is sending aninstant message to his friend using the smart phone. Since this type ofnotification is less important than what the user is currently doingwith his phone (i.e., sending a message), it may not be desirable (e.g.,considered too invasive) to interrupt the user's message-sendingactivities only to show the coupon to the user. Thus, the coupon may betemporarily stored on the user's smart phone, and shown to the userafter the user has completed sending the message.

In particular embodiments, when selecting specific notifications to bepushed to a specific user's device at specific times, the selections maybe based on various factors. This disclosure contemplates any relevantfactor. In particular embodiments, given a specific user and a specifictime, one or more notifications may be selected to be pushed to theuser's device based on, without limitation, the current time (e.g.,morning vs. afternoon vs. evening, or weekdays vs. weekends), thecurrent location of the user (e.g., work vs. home, restaurant, shops,theater, etc.), which may be derived from the GPS coordinates or thecommunication signals of the user's device or the Internet Protocol (IP)address of the user's device, the current activity of the user (e.g., ina meeting, making a phone call, eating lunch or dinner, watching amovie, etc.). The notifications may also be selected based on the user'ssocial information or social activities. For example, if the user has aclose social connection (e.g., a family member or a friend), thennotifications about the current status of the user's social connectionmay be pushed to the user's device from time to time. If the user takesany action in connection with an entity on the social-networking system,notifications about the entity may be pushed to the user's device fromtime to time.

Each user has a set of social connections (e.g., families, friends,coworkers, business associates, etc.). Among them, the user may considersome of them more important than others. For example, a user mayconsider immediate family members (e.g., spouses, children, or parents)or long-term good friends more important than casual acquaintances. Inparticular embodiments, notifications relating to people who are closeror more important to a user may be pushed more frequently than thoserelating to people who are less important to the user. In addition, inparticular embodiments, notifications relating to people who are closeror more important to a user may be designated as interruptivenotifications, while notifications relating to people who are lessimportant to the user may be designated as non-interruptivenotifications. For example, suppose that a user is browsing the webusing his mobile device when his wife sends an instance message. Such amessage from the user's wife (i.e., a person considered to be veryimportant to the user) may be designated as interruptive message so thatthe user can read and respond to the message immediately upon receivingit.

In particular embodiments, advertisements may optionally be pushed to auser's device, especially if a specific user does not object to suchkind of information or is interested in a particular product. Forexample, if the user has mentioned a product in a message posted on thesocial-networking system, advertisements about that product may bepushed to the user's device. If the user has mentioned a person (e.g.,expressing an interest or a liking in a celebrity), the current statusof that person may be pushed to the user's device. If the user hasindicated that he/she likes something or someone (e.g., a product, aplace, a movie, a book, a celebrity, etc.), then notifications aboutwhat or whom the user likes may be pushed to the user's device. If theuser likes a web page, then notifications about the entity with whichthe content of the web page is concerned may be pushed to the user'sdevice. In particular embodiments, certain types of notifications (e.g.,advertisements) may be pushed to a user's device less frequently thanother types of notifications (e.g., messages from friends) so that theuser is not annoyed with them.

In particular embodiments, for a given user and a given notification, arelevance score may be computed for the notification with respect to theuser, which indicates how relevant the notification is to the user. Ifthe notification is considered relevant to the user (e.g., having a highrelevance score), then the notification may be pushed to the user'sdevice. Conversely, if the notification is considered not sufficientlyrelevant to the user (e.g., having a low relevance score), then thenotification is not pushed to the user's device. In particularembodiments, the relevance score of a notification with respect to auser may be determined based on various factors, such as, withoutlimitation, a location value, which compares the location of the entityof the notification and the current location of the user, an interestvalue, which indicates whether the entity of the notification is or isnot included in the user's interests, a time value, which determineswhether the current time is within the delivery time range for theentity of the notification, and a connection value, which indicates thenumber of the user's social connections are associated with the entityof the notification. These different values may be combined to determinethe relevance score. Computing notification relevance score is describedin more detail in U.S. patent application Ser. No. 12/976,755, entitled“Pricing Relevant Notifications Provided to a User Based on Location andSocial Information”, filed on Dec. 22, 2010, which is incorporated byreference in its entirety and for all purposes.

FIG. 1 illustrates an example client-server environment 100 in which acommunication may be pushed to a client device. In particularembodiments, the client device may be a mobile device associated with auser. There may be any number of servers 110, 120, 130 of various typesand any number of clients 140 of various types. Each server 110, 120, or130 may include hardware, software, or embedded logic components or acombination of two or more such components for carrying out theappropriate functionalities implemented or supported by server 110, 120,or 130. In particular embodiments, servers 110, 120, and 130 may bearranged in tiers. For example, there may be one or more web servers 110for hosting a social-networking website. Each web server 110 may beconnected with one or more channel servers 120. Each channel server 120may be connected with one or more edge servers 130. Web servers 110,channel servers 120, and edge servers 130 may each perform some of thefunctionalities or operations supported by the social-networkingwebsite. For example, web servers 110 may host a network application ora web-based application, such as a social-networking application orwebsite. Channel servers 120 may monitor and manage the availablecommunication channels (e.g., media downloading or uploading, instantmessaging, posting, emailing, chatting, presence, etc.) for the users ofthe application hosted by web servers 110. Edge servers 130 may maintainnetwork or communication connections with user devices (e.g., clients140) for messaging and other accesses. In addition, edge servers 130 mayfunction as proxies for web servers 110. Clients 140 may communicatewith web servers 110 through edge servers 130. In particularembodiments, servers 110, 120, and 130 and clients 140 may each have aunique identifier. For example, each server 110, 120, and 130 may beidentified by its unique IP address, and each client 140 may beidentified by its unique device identifier.

By using multiple servers, the workload of the social-networking websitemay be shared and balanced among the multiple servers and thus, theperformance of the social-networking website may be improved. Forexample, the social-networking website may have hundreds of millions ofusers around the world, and at any given time, a great number of theseusers may be connected to the website through their respective userdevices. New users may continually join the website as well. These usersmay be shared and balanced among multiple channel servers 120 to beserviced. In particular embodiments, a hash algorithm may be applied tothe user identifier (e.g., the username or account number) of each userto determine to which channel server 120 a specific user is assigned. Inaddition or alternatively, channel servers 120 may be placed atdifferent physical locations around the world, and a user may beassigned to a channel server 120 that is relatively close (e.g., interms of physical distance) to the user's device. For example, a userlocated in Japan may be assigned to a channel server 120 located inJapan or China; while a user located in England may be assigned to achannel server 120 located in France.

In particular embodiments, each client 140 may be associated with a useras a user device. Each client 140 may be a mobile or non-mobile deviceand connected to a network wirelessly or through a wired connection. Inparticular embodiments, when a user connects with the social-networkingwebsite through his/her client 140 (i.e., the user device), client 140may establish one or more connections with an edge server 130. Eachconnection may be a TCP/IP connection. More specifically, client 140 maybe connected with an edge server 130 that is connected to the channelserver 120 to which the user of client 140 is assigned.

For example, suppose that a specific user, A, is assigned to a specificchannel server, 120-A (e.g., as a result of applying a hash algorithm tothe user identifier of user A). When user A connects with thesocial-networking website through his user device, 140-A, client 140-Amay establish one or more connections with an edge server, 130-A, thatis connected with channel server 120-A. Similarly, suppose that anotheruser, B, is assigned to a different channel server, 120-B (e.g., again,as a result of applying the hash algorithm to the user identifier ofuser B). When user B connects with the social-networking website throughhis user device, 140-B, client 140-B may establish one or moreconnections with an edge server, 130-B, that is connected with channelserver 120-B.

In particular embodiments, each edge server 130 may be connected withone or more clients 140 and service these clients 140. A specific client140 associated with a specific user may be connected with different edgeservers 130 connected to the channel server 120 to which the user isassigned at different times. For example, suppose that multiple edgeservers 130, including edge server 130-A, are connected with channelserver 120-A, and user A is assigned to channel server 120-A. Furthersuppose that client 140-A associated with user A is connected with edgeserver 130-A. Then, client 140-A is disconnected from edge server 130-A(e.g., user A has disconnected the network connection of client 140-A orshut down client 140-A). Subsequently, when user A again connects withthe social-networking website through client 140-A, client 140-A mayeither be connected with edge server 130-A again, or with another edgeserver that is also connected with channel server 120-A. In particularembodiments, edge servers 130 may be placed at different physicallocations around the world, and a client 140 may be connected with anedge server 130 that is relatively close (e.g., in terms of physicaldistance) to that client 140. In addition or alternatively, a client 140may be connected with an edge server 130 based on the current workloadof edge servers 130. For example, in the case where multiple edgeservers 130 are connected with channel server 120-A, to which user A isassigned, when client 140-A associated with user A needs to establish aconnection with one of the edge servers 130 connected with channelserver 120-A, the edge server currently services the least number ofclients may be selected.

In particular embodiments, when a client 140 first establishes aconnection with an edge server 130, client 140 may go through aregistration process with edge server 130. During the registrationprocess, client 140 may send its device identifier to edge server 130.Edge server 130 may forward the device identifier of client 140 to thechannel server 120 connected with edge server 130. In particularembodiments, when client 140 disconnects from edge server 130, edgeserver 130 may again send the device identifier of client 140 to thechannel server 120 connected with edge server 130. In particularembodiments, a channel server 120 may maintain, for each edge server 130connected with it, a list of clients 140 currently connected with thatedge server 130. This information may be stored in a lookup table. Forexample, suppose that channel server 120-A is connected with 6 edgeservers, 130-A1 to 130-A6. The following illustrates an example tablethat may be used by channel server 120-A to keep track of clientscurrently connected with each of edge servers 130-A1 to 130-A6.

EXAMPLE LOOKUP TABLE USED BY A CHANNEL SERVER EDGE EDGE SERVER IPCLIENTS CONNECTED WITH SERVER ADDRESS EDGE SERVER 130-A1 162.54.89.221-3985, 65-1895, 85-7164 130-A2 162.54.78.54 25-1058, 21-4872 130-A3162.54.78.160 45-9275, 13-6185, 01-6719, 2917 130-A4 162.54.89.12406-7265, 54-3147 130-A5 162.54.78.18 37-8375, 75-8125, 92-7250 130-A6162.54.78.32 51-5017

In the above example table, each client is identified by a uniquecombination of user identifier and device identifier (e.g., a pair ofnumbers, where the first number represents the user identifier and thesecond number represents the device identifier), and each edge server isidentified by its IP address. Note that it is possible for the same userto have multiple user devices connected with the same or different edgeservers 130 at the same time. For example, in the above table, the userwhose identifier is “21” has two devices whose identifiers are “3985”and “4872”, respectively. These two devices are connected with two edgeservers 130-A1 and 130-A2, respectively.

In particular embodiments, a user may store, in his/her user profilewith the social-networking system, the identifiers of his/her userdevices. Based on this information, the social-networking system may beable to determine which client 140 is associated with which specificuser. In particular embodiments, when the social-networking system needsto push a notification to a specific user (e.g., user A), a web server110 may determine to which channel server 120 user A is assigned (e.g.,channel server 120-A). For example, web server 110 may map theidentifier of user A to channel server 120-A by applying a hashalgorithm to the identifier of user A. The web server 110 connected withchannel server 120-A may send the notification to channel server 120-A.Channel server 120-A may then determine whether user A has a user device(e.g., client 140-A) that is currently connected with one of edgeservers 130 connected with channel server 120-A using information storedin a lookup table (e.g., the example lookup table illustrated above).That is, channel server 120-A may map the combination of the useridentifier of user A and the device identifier of client 140-A to anedge server (e.g., edge server 130-A) connected with channel server120-A using the lookup table maintained by channel server 120-A. If nouser device associated with user A is currently connected with any edgeserver 130 connected with channel server 120-A, channel server 120-A maystore the notification to be pushed to client 140-A at a future timewhen client 140-A is connected with one of edge servers 130 connectedwith channel server 120-A. On the other hand, if client 140-A iscurrently connected with one of edge servers 130 (e.g., edge server130-A) connected with channel server 120-A, channel server 120-A maysend the notification to edge server 130-A, which in turn may push thenotification to client 140-A. In particular embodiments, when a userneeds to send data (e.g., a message or a response to a notificationreceived at the user's device) to the social-networking website, theuser's device (e.g., client 140-A) may directly send the data to a webserver 110 hosing the social-networking website. Alternatively, edgeserver 130-A may function as a proxy for web servers 110. In this case,client 140-A may communication with web servers 110 via edge server103-A. FIG. 2 illustrates an example of pushing a notification to auser's device as described above.

In particular embodiments, a user device (e.g., a client 140) mayinclude hardware, firmware, and software. FIG. 3 illustrates an exampleclient device 140. In particular embodiments, client device 140 may be asmart phone (e.g., iPhone or Blackberry), which is a mobile telephonethat offers more advanced computing ability and connectivity than atraditional mobile phone. It may be considered as a handheld computerintegrated with a mobile phone. In particular embodiments, client device140 may be a netbook or tablet computer (e.g., iPad). In particularembodiments, client device 140 may be connected to a network through awireless connection.

In particular embodiments, client device 140 may include hardware 210and software 220. In particular embodiments, hardware 210 may includeany number of hardware components such as, for example and withoutlimitation, processor 211, memory 212, storage 213, transceiver 214,input/output device 215 (e.g., display, touch screen, keypad,microphone, speaker, etc.), camera 216, global positioning system (GPS)sensor 217, sensors hub 218, notification control switch 219, RFIDreader 241, RF sensor 242, and so on. This disclosure contemplates anysuitable hardware components. Sensors hub 218, notification controlswitch 219, RFID reader 241, and RF sensor 242 are described in moredetail below. In particular embodiments, some or all of a user's userdata may be stored in storage 213.

In particular embodiments, software 220 may include an operating system221, which may include a kernel 231 and/or any number of device drivers232 corresponding to some of the hardware components available on clientdevice 140. Operating system 221 may be selected for client device 140based on the actual type of device client device 140 is. For example, ifclient device 140 is a mobile device (e.g., a smart phone), thenoperating system 221 may be a mobile operating system such as, forexample and without limitation, Microsoft's Windows Mobile, Google'sAndroid, Nokia's Symbian, Apple's iOS, and Samsung's Bada.

In particular embodiments, there may be a connection pool manager 222residing and executing on client device 140, which may be implemented ascomputer software. Connection pool manager 222 is described in moredetail below.

In particular embodiments, one or more software applications 223 may beexecuted on client device 140. In particular embodiments, they may benative applications installed and residing on client device 140. Forexample, one application (e.g., Google Maps) may enable a device user toview a map, search for addresses and businesses, and get directions; asecond application may enable the device user to read, send, and receiveemails; a third application (e.g., a web browser) may enable the deviceuser to browse and search the Internet; a fourth application may enablethe device user to take photos or record videos using camera 216; afifth application may allow the device user to receive and initiate VoIPand/or cellular network calls, and so on. In particular embodiments,there may be a software application (e.g., notification control 241)that enables the device user to manage the notifications pushed toclient device 140. Notification control 241 is described in more detailbelow. Each software application 220 may have a user interface and mayimplement one or more specific functionalities. Each softwareapplication 220 may include one or more software modules implementingthe individual functionalities. The executable code of softwareapplications 220, including notification control 241, may be stored in acomputer-readable and non-transitory medium (e.g., storage 213 or memory212) on client device 140.

Managing Notifications Pushed to a User Device

Sometimes, a user may not wish to receive notifications pushed tohis/her user device. For example, the user may be involved in some typeof activity (e.g., in a meeting, having a meal, on the phone, or in atheatre) and not wish to be disturbed or interrupted by notificationspushed to his/her user device. Particular embodiments may enable a userto manage the notifications pushed to his/her user device throughvarious means.

In particular embodiments, a user device may include a hardwarecomponent (e.g., notification control 219 illustrated in FIG. 3) in theform of, for example, a switch or a button. The user may turn on or offthe notifications pushed to his/her user device by turning on or offnotification control switch 219. For example, when the user turns onnotification control switch 219, the user device establishes aconnection with a server (e.g., an edge server 130 illustrated in FIGS.1 and 2) and receives notifications pushed to it by the edge server.However, when the user turns off notification control switch 219, theedge server does not push any notification to the user device. Inaddition, the user device may be disconnected from the edge server.

In addition or alternatively, in particular embodiments, a user devicemay include a software application (e.g., notification control 241illustrated in FIG. 3) that has a user interface (e.g., an on/off icon).The user may turn on and off the notifications pushed to his/her userdevice by clicking on the on/off icon. For example, the first time theuser clicks on the icon, the notifications may be turned off, and thesecond time the user clicks on the icon, the notifications may be turnedon again, and so on. When the notifications are turned off, nonotification is pushed to the user device. In addition, the user devicemay be disconnected from the edge server.

Here, notification control 219 and notification control 241 essentiallyimplement the same functionalities (i.e., turning on and off thenotifications pushed to the user device). Notification control 219 isimplemented as a hardware switch, while notification control 241 isimplemented as a software switch. A user device may have both thehardware switch and the software switch, or only the hardware switch, oronly the software switch.

FIG. 4 illustrates an example method for turning on or off notificationspushed to a user device using either a hardware or a software switch. Inparticular embodiments, a user may turn on notifications using thehardware or software switch on his/her user device, as illustrated inSTEP 411. This indicates that the user is willing to receivenotifications pushed to his/her user device. The user device may checkwhether it is currently connected with a sever (e.g., an edge server 130illustrated in FIGS. 1 and 2), as illustrated in STEP 412. If the userdevice is not currently connected with any edge server, the user devicemay establish a connection with an edge server, as illustrated in STEP413.

To establish a connection with an edge server, in particularembodiments, the user device may access the social-networking websitehosted by the web servers. A web server may map the user's identifier toa channel server. The channel server to which the user is assigned mayselect one of the edge servers connected to it for the user. Theselected edge server may then establish a connection with the userdevice. The user device may go through the registration processdescribed above with the selected edge server.

In particular embodiments, the user device may send a message to a webserver hosting the social-networking website, indicating that the userhas turned on notifications and is willing to receive notificationspushed to his/her user device, as illustrated in STEP 414. Thereafter,the social-networking website may push notifications to the user'sdevice.

In particular embodiments, a user may turn off notifications using thehardware or software switch on his/her user device, as illustrated inSTEP 421. This indicates that the user is not willing to receivenotifications pushed to his/her user device. The user device may send amessage to a web server hosting the social-networking website,indicating that the user has turned off notifications and is not willingto receive notifications pushed to his/her user device, as illustratedin STEP 422. Thereafter, the social-networking website may stop pushingnotifications to the user's device. Optionally, in particularembodiments, the user device may sever its connection with and bedisconnected from the edge server with which it has been connected, asillustrated in STEP 423.

In addition to hardware and software switches, notifications may becontrolled by other means. In particular embodiments, whether to pushnotifications to a user's device may be determined based on theinformation in the user's calendar. Often, people may schedule events,such as appointments, meetings, or activities, in their calendars. Eachentry in the calendar may have a time period, an event type (e.g., thenature of the event), and may optionally identify the participants ofthe event. The social-networking system may access a user's calendarinformation and determine when is or is not a good time to pushnotifications to the user's device. For example, if a user has a meetingscheduled on Monday between 10:00 am to 11:30 am in the user's calendar,then during this time, it may not be desirable to push notifications tothe user's device as the notifications may disturb and distract the userfrom participating in the meeting. On the other hand, if there is noevent scheduled on Monday between 1:00 pm and 3:00 pm in the user'scalendar, then during this time, notifications may be pushed to theuser's device as the user probably will not be disturbed by and thus getannoyed at the notifications.

In particular embodiments, a user may specify to the social-networkingsystem (e.g., in the user's profile with the social-networking system)the types of events, if found in the user's calendar, during which theuser does not wish to receive notifications at his/her user device. Forexample, a user may specify that during meetings, meals, and familyfunctions, the user does not wish to receive notifications at her userdevice. In this case, whenever an event of the type specified by theuser is found in her calendar, the social-networking system may refrainfrom pushing notifications to her user device during the event (i.e.,while the event takes place). On the other hand, if an event not of thetype specified by the user is found in her calendar, thesocial-networking system may still push notifications to her user devicewhile the event takes place.

In particular embodiments, a user may specify to the social-networkingsystem (e.g., in the user's profile with the social-networking system)specific time periods during which the user does not wish to receivenotifications at his/her user device, regardless of whether any eventsare scheduled during these time periods. For example, a user may specifythat on weekdays between 10:00 pm and 6:00 am and on weekends between4:00 pm and 10:00 am the user does not wish to receive notifications athis user device. In this case, during such a time period, thesocial-networking system may refrain from pushing notifications to hisuser device even if no event has been scheduled during the time periodin the user's calendar.

In particular embodiments, whether to push notifications to a user'sdevice may be determined based on the location of the user's device(e.g., as determined by the GPS coordinates of the user's device). Thesocial-networking system may push notifications to the user's deviceonly when the device is at certain locations (e.g., the user's office orhome, shopping malls, etc.) but may refrain from pushing notificationsto the user's device only when the device is at other locations (e.g.,movie theaters, restaurants, etc.).

In particular embodiments, a user may specify to the social-networkingsystem (e.g., in the user's profile with the social-networking system)specific locations where the user does not wish to receive notificationsat his/her user device. When the user's device is at such a location, nonotification is pushed to the user's device. For example, a user mayspecify that she does not wish to receive notifications at her userdevice when she is at the Memorial Opera House in San Francisco, theJoya Restaurant in Palo Alto, the Tech Museum in San Jose, etc. Thecoordinates of each of these locations may be determined (e.g., from amap database). The current location of the user's device may bedetermined based on the GPS coordinates provided by the GPS sensor ofthe device (e.g., GPS sensor 217 illustrated in FIG. 3). When the GPScoordinates of the user device match the coordinates of one of thelocations specified by the user, the social-networking system mayrefrain from pushing notifications to the user's device.

In particular embodiments, whether to push notifications to a user'sdevice may be determined based on the proximity of the user's device toa person or an object. Often, a person or an object may carry or includea Radio-Frequency Identification (RFID) tag. RFID is a technology thatuses communication via radio waves to exchange data between a RFIDreader and a RFID tag attached to a person or object, for the purposeof, for example, identification and tracking. In particular embodiments,a user device may include a RFID reader (e.g., RFID reader 241illustrated in FIG. 3). The RFID reader of the user device may scan RFIDtags attached to people and objects. Based on the scanned information,the user device may determine its proximity to a RFID tag, and thus tothe person or object carrying the RFID tag. In particular embodiments,notifications may not be pushed to a user's device when the RFID readerof the device indicates that the device is in close proximity to aperson or object carrying a specific type of RFID tag. For example, auser, who is a parent, may attached a RFID tag to his young child forsafety reasons. The user may specify to the social-networking systemthat he does not wish to receive notifications at his user device whenthe user device is in close proximity to his young child. The RFIDreader of the user device may detect the device's proximity to the RFIDtag attached to the child. If the user device is sufficiently close tothe RFID tag attached to the child, the user device may inform thesocial-networking system, and the social-networking system may refrainfrom pushing the notifications to the user device until the user devicemoves sufficiently away from the RFID tag attached to the child.

Near Field Communication (NFC) is a set of short-range wirelesstechnologies, typically requiring a distance of 4 cm or less. NRCgenerally involves an initiator and a target. The initiator activelygenerates an RF (radio frequency) field that can power a passive target.In particular embodiments, NFC may also be used to determine a userdevice's proximity to a person or object. The user device may be eitherthe initiator or the target. For example, the user device may include asuitable RF sensor (e.g., RF sensor 242 illustrated in FIG. 3) or a RFfield generator. In particular embodiments, notifications may not bepushed to a user's device if the user device determines, based on NRCtechnologies, that it is in close proximity to a person or objectspecific by the user.

Performing Selected Operations with a Low Power-Consuming Processor

In particular embodiments, a user device may include various types ofsensors and other input/output devices for providing additional inputsand facilitate various functionalities implemented by the user device.For example, in FIG. 3, device 140 includes GPS sensor 217 for locationpositioning. Other types of sensors that may be included in a userdevice may include, for example and without limitation, altimeter foraltitude positioning, motion sensor for determining the orientation of auser device, light sensor for photographing function with a camera(e.g., camera 216 illustrated in FIG. 3), temperature sensor formeasuring ambient temperature, biometric sensor for securityapplications (e.g., fingerprint reader), and so on. These sensors mayform a sensor subsystem on the user device. Other input/output (I/O)devices may include radio network interfaces implemented by transceiver214 in combination with additional hardware, software and/or firmware.

In particular embodiments, in addition to the main or primary processors(e.g., processor 211 illustrated in FIG. 3), a user device may have oneor more other (e.g., secondary) processors for managing the sensors andother I/O devices included in the user device. In particularembodiments, these “secondary” processors that manage the sensors may below power-consuming processors and may be referred to as a sensors hub(e.g., sensors hub 218 illustrated in FIG. 3). A sensors hub included ina user device may, for example, control the sensors, manage power forthe sensors, process sensor inputs, aggregate sensor data, and performcertain sensor functions. This may, to a certain extent, free up themain processor of the user device to perform other operations (e.g.,executing the operating system or software applications).

As described above in connection with FIGS. 1 and 2, a user device(e.g., a client 140 illustrated in FIGS. 1 and 2) may be connected witha server (e.g., an edge server 130 illustrated in FIGS. 1 and 2)wirelessly or through a wired connection. From time to time, the servermay push notifications to the user device over the connection betweenthem. Instead of establishing a new connection each time the serverwants to push a notification to the user device, a connection betweenthe server and the user device, once established, may be kept “alive”(i.e., connected) for some period of time so that the server may pushmultiple notifications to the user device over the same connection. Thismay help save some of the resources needed to reestablish the connectionagain and again. FIG. 5 illustrates an example method that a sensors hubmay perform certain tasks.

In particular embodiments, while the server and the user device areconnected, the server may ping the user device periodically to determinewhether the user device is still available (i.e., whether the connectionwith the user device is still alive). The server may send a “keep-alive”ping (e.g., a small data packet) to the user device over the connection.If the user device is still available (e.g., at the other end of theconnection) and receives the “keep-alive” ping, then the user device maysend an acknowledgement back to the server over the connection, in whichcase the server knows that the user device is still available and theconnection is still alive. On the other hand, if the user device is nolonger available, then no acknowledgement to the “keep-alive” ping maybe sent back by the user device, in which case the server knows that theuser device is no longer available and the connection no longer existsbetween the server and user device.

When a user device receives a message, a network interface may transmitthe message data into memory 212 and transmit an interrupt that causes aprocessor (e.g., processor 211 illustrated in FIG. 3) to process themessage. In particular embodiments, when a user device receives a“keep-alive” ping from a server, as illustrated in STEP 411, instead ofhaving the main processor of the user device answer the “keep-alive”ping, a sensors hub of the user device answers the “keep-alive” pingfrom the server and sends a response to the server, as illustrated inSTEP 412. In one implementation, this can be implemented by having thesensors hub (e.g., sensors hub 218 illustrated in FIG. 3) interceptand/or filter interrupts while the main processor (e.g., processor 211illustrated in FIG. 3) is in sleep mode. In alternative embodiment, thenetwork interface may be programmed to transmit interrupts to thesensors hub while the main processor is in sleep mode. A sensors huboften consumes less power than a main processor. A server may send many“keep-alive” pings to a user device during the lifetime of a connectionbetween them. By having the sensors hub answer the “keep-alive” pingsand send back the acknowledgements to the server, less power of the userdevice may be needed.

Often, a user device may have its main or primary processor go into asleep mode when no operation needs to be performed by the main processorto save power. For example, when the user device is in stand-by mode,its main processor may go into sleep mode. When the user device receivesa “keep-alive” ping from the server while its main processor is in sleepmode, the main processor does not need to be woken up to answer the“keep-alive” ping, since the sensors hub is able to answer the“keep-alive” ping instead. Note that the sensors hub may answer the“keep-alive” pings regardless of whether the main processor is currentlyin sleep mode.

In particular embodiments, the user device may receive anon-interruptive notification pushed to the user device by the server,as illustrated in STEP 421. If the main processor of the user device iscurrently in sleep mode, the sensors hub may store the non-interruptivenotification on the user device, as illustrated in STEP 422. Thenotification may be presented to the user at a future time when the mainprocessor wakes up.

As described above, non-interruptive notifications do not require auser's immediate attention. For example, they may be low-prioritycommunications. Thus, it often is not necessary to presentnon-interruptive notifications to the user immediately after they arereceived. If the main processor of the user device is currently in anoperational mode (i.e., awake) when a non-interruptive notification isreceived, then the non-interruptive notification may be presented to theuser right away. However, if the main processor of the user device iscurrently in sleep mode when a non-interruptive notification isreceived, then it is not necessary to wake up (e.g., transmit aninterrupt or other message) the main processor for the sole purpose ofpresenting the non-interruptive notification to the user immediately.The sensors hub may store the non-interruptive notification forpresentation to the user at a future time. This may save some power forthe user device since the main processor is not waken up each time anon-interruptive notification is received at the user device.

In particular embodiments, the user device may receive an interruptivenotification pushed to the user device by the server, as illustrated inSTEP 431. As described above, interruptive notifications require auser's immediate attention. For example, they may be high-prioritycommunications. If the main processor of the user device is currently insleep mode, the sensors hub may wake up the main processor to handle theinterruptive notification, as illustrated in STEP 432. In addition,while the main processor of the user device is in sleep mode, thesensors hub may monitor the operational status of the user device. Ifthere is any task that needs to be performed by the main processorimmediately, the sensors hub may wake up the main processor to performthe task. Of course, whether a task needs to be performed by the mainprocessor immediately may depend on the configuration or thespecification of the user device (e.g., including hardware and softwareconfigurations or specifications), which may be specified by the user orthe designer or the manufacturer of the user device.

Managing a Pool of Network Connections for a User Device

In particular embodiments, a “connection pool” may be a cache of networkor communication connections between two devices maintained so that theconnections may be reused when the two devices need to communicate(e.g., send data) to each other. In particular embodiments, either oneor both devices may have a connection pool manager that manages thecache of connections in the pool. For example, in FIG. 3, client device140 includes connection pool manager 222.

As described above in connection with FIGS. 1 and 2, a user device(e.g., a client 140 illustrated in FIGS. 1 and 2) may be connected witha server (e.g., an edge server 130 illustrated in FIGS. 1 and 2)wirelessly or through a wired connection. In particular embodiments,there may be a pool of cached network or communication connections(e.g., wired or wireless connections) between the user device and theedge server. For example, each connection in the pool may be a socketconnection. Each connection in the pool may support various network orcommunication protocols, such as, for example and without limitation,TCP/IP (the Internet Protocol Suite), and HTTP (Hypertext TransferProtocol). In particular embodiments, if a server is connected withmultiple user devices, then there is a connection pool between theserver and each of the user devices. That is, each user device has itsown connection pool and does not need to share the same connection poolwith another user device also connected with the same server. Of course,a connection pool may be maintained between any two devices.

FIG. 6 illustrates an example connection pool 600, which includesconnections 610-A to 610-E, maintained between an edge server 130 and aclient device 140 (i.e., a user device). Note that only a fewconnections are illustrated in FIG. 6 to simplify the discussion. Inpractice, a connection pool may include any number of network orcommunication connections. As described above, client 140 may include aconnection pool manager 222 and any number of software applications 223.

In particular embodiments, some of the connections (e.g., connection610-A) in the pool may be reserved for and dedicated to certain specifictasks. For example, connection 610-A may be reserved for receivingnotifications pushed to client 140 from a social-networking system(e.g., through edge server 130) and/or keep alive messages as discussedabove. Other asynchronous tasks (e.g., data logging) may also havededicated connections in connection pool 600. Other connections (e.g.,connections 610-B to 610-E) in the pool may be shared among softwareapplications 223. In particular embodiments, connection pool manager 222may manage the sharing of the connections in the pool among softwareapplications 223.

FIG. 7 illustrates an example method for sharing connections in aconnection pool among multiple software applications executing on aclient. In particular embodiments, suppose that the client hasestablished and maintains a pool (e.g., a set) of network orcommunication connections, and the client has a connection pool manager(e.g., implemented as computer software) for managing the connections inthe pool. A software application (e.g., a web browser or an emailapplication) executing on the client may initiate a request to connectto a server, as illustrated in STEP 711. In particular embodiments, theconnection pool manager executing on the client may intercept therequest, as illustrated in STEP 712, so that the operating system of theclient does not establish a new connection between the client and theserver for the software application in response to the request.

In particular embodiments, the connection pool manager may select anavailable connection (e.g., an available socket connection) from theconnection pool and assign this available connection to the softwareapplication, as illustrated in STEP 713. In particular embodiments, aconnection in the pool is available if it is not reserved for anddedicated to some types of tasks (e.g., for push notifications orasynchronous tasks) and it is not currently used by any softwareapplication executing on the client. The software application may thenuse this connection to communicate with the server. When the softwareapplication is done with communicating with the server, the connectionis released and returned to the connection pool so that it may be usedby another software application subsequently. In some implementations,additional connections can be opened, if all open connections have beenallocated to a given task.

In particular embodiments, the connection pool manager may keep track ofthe current status of each connection in the pool, such as, whether aconnection is reserved for and dedicated to a specific task and whethera connection is currently used by a software application. This allowsthe connection pool manager to determine, at any given time, whichconnection in the pool is currently available and may be assigned to asoftware application making a network request.

By maintaining a connection pool so that the connections in the pool,once established, may be shared and reused, it is not necessary that anew connection needs to be established each time an application or theoperating system of the user device needs a network or communicationconnection. This may improve performance for the user device by nothaving to do the handshakes necessary to establish the new connections.

If the user device is a mobile device having wireless connections (i.e.,the connections in the connection pool are wireless connections), thenthe mobile device may move from location to location (i.e., roam) orthere may be small interruptions in the wireless connectivity from timeto time. The wireless connections in the pool may or may not surviveroaming or the connectivity interruptions. For example, if aconnectivity interruption is small enough that the user device does notactually lose the connections all together, the connection pool maysurvive such an interruption. But if a connectivity interruption issevere enough, the connection pool may not be able to survive such aninterruption (i.e., the connections in the pool are lost), in which casenew connections may need to be established. As another example, supposethat the mobile device has roamed from one location to another locationand needs to be handed off to a different base station. This may causethe connections in the pool to be lost, in which case new connectionsmay need to be established (e.g., through the new base station).

Particular embodiments may be implemented in a network environment. FIG.8 illustrates an example network environment 800. Network environment800 includes a network 810 coupling one or more servers 820 and one ormore clients 830 to each other. In particular embodiments, network 810is an intranet, an extranet, a virtual private network (VPN), a localarea network (LAN), a wireless LAN (WLAN), a wide area network (WAN), ametropolitan area network (MAN), a portion of the Internet, or anothernetwork 810 or a combination of two or more such networks 810. Thisdisclosure contemplates any suitable network 810.

One or more links 850 couple a server 820 or a client 830 to network810. In particular embodiments, one or more links 850 each includes oneor more wireline, wireless, or optical links 850. In particularembodiments, one or more links 850 each includes an intranet, anextranet, a VPN, a LAN, a WLAN, a WAN, a MAN, a portion of the Internet,or another link 850 or a combination of two or more such links 850. Thisdisclosure contemplates any suitable links 850 coupling servers 820 andclients 830 to network 810.

In particular embodiments, each server 820 may be a unitary server ormay be a distributed server spanning multiple computers or multipledatacenters. Servers 820 may be of various types, such as, for exampleand without limitation, web server, news server, mail server, messageserver, advertising server, file server, application server, exchangeserver, database server, or proxy server. In particular embodiments,each server 820 may include hardware, software, or embedded logiccomponents or a combination of two or more such components for carryingout the appropriate functionalities implemented or supported by server820. For example, a web server is generally capable of hosting websitescontaining web pages or particular elements of web pages. Morespecifically, a web server may host HTML files or other file types, ormay dynamically create or constitute files upon a request, andcommunicate them to clients 830 in response to HTTP or other requestsfrom clients 830. A mail server is generally capable of providingelectronic mail services to various clients 830. A database server isgenerally capable of providing an interface for managing data stored inone or more data stores. In particular embodiments, a social-networkingsystem 822, implementing a social-networking website, may be hosted onone or more servers 820.

In particular embodiments, one or more data storages 840 may becommunicatively linked to one or more severs 820 via one or more links850. In particular embodiments, data storages 840 may be used to storevarious types of information. In particular embodiments, the informationstored in data storages 840 may be organized according to specific datastructures. In particular embodiments, each data storage 840 may be arelational database. Particular embodiments may provide interfaces thatenable servers 820 or clients 830 to manage, e.g., retrieve, modify,add, or delete, the information stored in data storage 840.

In particular embodiments, each client 830 may be an electronic deviceincluding hardware, software, or embedded logic components or acombination of two or more such components and capable of carrying outthe appropriate functionalities implemented or supported by client 830.For example and without limitation, a client 830 may be a desktopcomputer system, a notebook computer system, a netbook computer system,a handheld electronic device, or a mobile telephone. This disclosurecontemplates any suitable clients 830. A client 830 may enable a networkuser at client 830 to access network 830. A client 830 may enable itsuser to communicate with other users at other clients 830.

A client 830 may have a web browser 832, such as MICROSOFT INTERNETEXPLORER, GOOGLE CHROME or MOZILLA FIREFOX, and may have one or moreadd-ons, plug-ins, or other extensions, such as TOOLBAR or YAHOOTOOLBAR. A user at client 830 may enter a Uniform Resource Locator (URL)or other address directing the web browser 832 to a server 820, and theweb browser 832 may generate a Hyper Text Transfer Protocol (HTTP)request and communicate the HTTP request to server 820. Server 820 mayaccept the HTTP request and communicate to client 830 one or more HyperText Markup Language (HTML) files responsive to the HTTP request. Client830 may render a web page based on the HTML files from server 820 forpresentation to the user. This disclosure contemplates any suitable webpage files. As an example and not by way of limitation, web pages mayrender from HTML files, Extensible Hyper Text Markup Language (XHTML)files, or Extensible Markup Language (XML) files, according toparticular needs. Such pages may also execute scripts such as, forexample and without limitation, those written in JAVASCRIPT, JAVA,MICROSOFT SILVERLIGHT, combinations of markup language and scripts suchas AJAX (Asynchronous JAVASCRIPT and XML), and the like. Herein,reference to a web page encompasses one or more corresponding web pagefiles (which a browser may use to render the web page) and vice versa,where appropriate.

Particular embodiments may be implemented on one or more computersystems. FIG. 9 illustrates an example computer system 900. Inparticular embodiments, one or more computer systems 900 perform one ormore steps of one or more methods described or illustrated herein. Inparticular embodiments, one or more computer systems 900 providefunctionality described or illustrated herein. In particularembodiments, software running on one or more computer systems 900performs one or more steps of one or more methods described orillustrated herein or provides functionality described or illustratedherein. Particular embodiments include one or more portions of one ormore computer systems 900.

This disclosure contemplates any suitable number of computer systems900. This disclosure contemplates computer system 900 taking anysuitable physical form. As example and not by way of limitation,computer system 900 may be an embedded computer system, a system-on-chip(SOC), a single-board computer system (SBC) (such as, for example, acomputer-on-module (COM) or system-on-module (SOM)), a desktop computersystem, a laptop or notebook computer system, an interactive kiosk, amainframe, a mesh of computer systems, a mobile telephone, a personaldigital assistant (PDA), a server, or a combination of two or more ofthese. Where appropriate, computer system 900 may include one or morecomputer systems 900; be unitary or distributed; span multiplelocations; span multiple machines; or reside in a cloud, which mayinclude one or more cloud components in one or more networks. Whereappropriate, one or more computer systems 900 may perform withoutsubstantial spatial or temporal limitation one or more steps of one ormore methods described or illustrated herein. As an example and not byway of limitation, one or more computer systems 900 may perform in realtime or in batch mode one or more steps of one or more methods describedor illustrated herein. One or more computer systems 900 may perform atdifferent times or at different locations one or more steps of one ormore methods described or illustrated herein, where appropriate.

In particular embodiments, computer system 900 includes a processor 902,memory 904, storage 906, an input/output (I/O) interface 908, acommunication interface 910, and a bus 912. Although this disclosuredescribes and illustrates a particular computer system having aparticular number of particular components in a particular arrangement,this disclosure contemplates any suitable computer system having anysuitable number of any suitable components in any suitable arrangement.

In particular embodiments, processor 902 includes hardware for executinginstructions, such as those making up a computer program. As an exampleand not by way of limitation, to execute instructions, processor 902 mayretrieve (or fetch) the instructions from an internal register, aninternal cache, memory 904, or storage 906; decode and execute them; andthen write one or more results to an internal register, an internalcache, memory 904, or storage 906. In particular embodiments, processor902 may include one or more internal caches for data, instructions, oraddresses. This disclosure contemplates processor 902 including anysuitable number of any suitable internal caches, where appropriate. Asan example and not by way of limitation, processor 902 may include oneor more instruction caches, one or more data caches, and one or moretranslation lookaside buffers (TLBs). Instructions in the instructioncaches may be copies of instructions in memory 904 or storage 906, andthe instruction caches may speed up retrieval of those instructions byprocessor 902. Data in the data caches may be copies of data in memory904 or storage 906 for instructions executing at processor 902 tooperate on; the results of previous instructions executed at processor902 for access by subsequent instructions executing at processor 902 orfor writing to memory 904 or storage 906; or other suitable data. Thedata caches may speed up read or write operations by processor 902. TheTLBs may speed up virtual-address translation for processor 902. Inparticular embodiments, processor 902 may include one or more internalregisters for data, instructions, or addresses. This disclosurecontemplates processor 902 including any suitable number of any suitableinternal registers, where appropriate. Where appropriate, processor 902may include one or more arithmetic logic units (ALUs); be a multi-coreprocessor; or include one or more processors 902. Although thisdisclosure describes and illustrates a particular processor, thisdisclosure contemplates any suitable processor.

In particular embodiments, memory 904 includes main memory for storinginstructions for processor 902 to execute or data for processor 902 tooperate on. As an example and not by way of limitation, computer system900 may load instructions from storage 906 or another source (such as,for example, another computer system 900) to memory 904. Processor 902may then load the instructions from memory 904 to an internal registeror internal cache. To execute the instructions, processor 902 mayretrieve the instructions from the internal register or internal cacheand decode them. During or after execution of the instructions,processor 902 may write one or more results (which may be intermediateor final results) to the internal register or internal cache. Processor902 may then write one or more of those results to memory 904. Inparticular embodiments, processor 902 executes only instructions in oneor more internal registers or internal caches or in memory 904 (asopposed to storage 906 or elsewhere) and operates only on data in one ormore internal registers or internal caches or in memory 904 (as opposedto storage 906 or elsewhere). One or more memory buses (which may eachinclude an address bus and a data bus) may couple processor 902 tomemory 904. Bus 912 may include one or more memory buses, as describedbelow. In particular embodiments, one or more memory management units(MMUs) reside between processor 902 and memory 904 and facilitateaccesses to memory 904 requested by processor 902. In particularembodiments, memory 904 includes random access memory (RAM). This RAMmay be volatile memory, where appropriate. Where appropriate, this RAMmay be dynamic RAM (DRAM) or static RAM (SRAM). Moreover, whereappropriate, this RAM may be single-ported or multi-ported RAM. Thisdisclosure contemplates any suitable RAM. Memory 904 may include one ormore memories 904, where appropriate. Although this disclosure describesand illustrates particular memory, this disclosure contemplates anysuitable memory.

In particular embodiments, storage 906 includes mass storage for data orinstructions. As an example and not by way of limitation, storage 906may include an HDD, a floppy disk drive, flash memory, an optical disc,a magneto-optical disc, magnetic tape, or a Universal Serial Bus (USB)drive or a combination of two or more of these. Storage 906 may includeremovable or non-removable (or fixed) media, where appropriate. Storage906 may be internal or external to computer system 900, whereappropriate. In particular embodiments, storage 906 is non-volatile,solid-state memory. In particular embodiments, storage 906 includesread-only memory (ROM). Where appropriate, this ROM may bemask-programmed ROM, programmable ROM (PROM), erasable PROM (EPROM),electrically erasable PROM (EEPROM), electrically alterable ROM (EAROM),or flash memory or a combination of two or more of these. Thisdisclosure contemplates mass storage 906 taking any suitable physicalform. Storage 906 may include one or more storage control unitsfacilitating communication between processor 902 and storage 906, whereappropriate. Where appropriate, storage 906 may include one or morestorages 906. Although this disclosure describes and illustratesparticular storage, this disclosure contemplates any suitable storage.

In particular embodiments, I/O interface 908 includes hardware,software, or both providing one or more interfaces for communicationbetween computer system 900 and one or more I/O devices. Computer system900 may include one or more of these I/O devices, where appropriate. Oneor more of these I/O devices may enable communication between a personand computer system 900. As an example and not by way of limitation, anI/O device may include a keyboard, keypad, microphone, monitor, mouse,printer, scanner, speaker, still camera, stylus, tablet, touch screen,trackball, video camera, another suitable I/O device or a combination oftwo or more of these. An I/O device may include one or more sensors.This disclosure contemplates any suitable I/O devices and any suitableI/O interfaces 908 for them. Where appropriate, I/O interface 908 mayinclude one or more device or software drivers enabling processor 902 todrive one or more of these I/O devices. I/O interface 908 may includeone or more I/O interfaces 908, where appropriate. Although thisdisclosure describes and illustrates a particular I/O interface, thisdisclosure contemplates any suitable I/O interface.

In particular embodiments, communication interface 910 includeshardware, software, or both providing one or more interfaces forcommunication (such as, for example, packet-based communication) betweencomputer system 900 and one or more other computer systems 900 or one ormore networks. As an example and not by way of limitation, communicationinterface 910 may include a network interface controller (NIC) ornetwork adapter for communicating with an Ethernet or other wire-basednetwork or a wireless NIC (WNIC) or wireless adapter for communicatingwith a wireless network, such as a WI-FI network. This disclosurecontemplates any suitable network and any suitable communicationinterface 910 for it. As an example and not by way of limitation,computer system 900 may communicate with an ad hoc network, a personalarea network (PAN), a local area network (LAN), a wide area network(WAN), a metropolitan area network (MAN), or one or more portions of theInternet or a combination of two or more of these. One or more portionsof one or more of these networks may be wired or wireless. As anexample, computer system 900 may communicate with a wireless PAN (WPAN)(such as, for example, a BLUETOOTH WPAN), a WI-FI network, a WI-MAXnetwork, a cellular telephone network (such as, for example, a GlobalSystem for Mobile Communications (GSM) network), or other suitablewireless network or a combination of two or more of these. Computersystem 900 may include any suitable communication interface 910 for anyof these networks, where appropriate. Communication interface 910 mayinclude one or more communication interfaces 910, where appropriate.Although this disclosure describes and illustrates a particularcommunication interface, this disclosure contemplates any suitablecommunication interface.

In particular embodiments, bus 912 includes hardware, software, or bothcoupling components of computer system 900 to each other. As an exampleand not by way of limitation, bus 912 may include an AcceleratedGraphics Port (AGP) or other graphics bus, an Enhanced Industry StandardArchitecture (EISA) bus, a front-side bus (FSB), a HYPERTRANSPORT (HT)interconnect, an Industry Standard Architecture (ISA) bus, an INFINIBANDinterconnect, a low-pin-count (LPC) bus, a memory bus, a Micro ChannelArchitecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, aPCI-Express (PCI-X) bus, a serial advanced technology attachment (SATA)bus, a Video Electronics Standards Association local (VLB) bus, oranother suitable bus or a combination of two or more of these. Bus 912may include one or more buses 912, where appropriate. Although thisdisclosure describes and illustrates a particular bus, this disclosurecontemplates any suitable bus or interconnect.

Herein, reference to a computer-readable storage medium encompasses oneor more non-transitory, tangible computer-readable storage mediapossessing structure. As an example and not by way of limitation, acomputer-readable storage medium may include a semiconductor-based orother integrated circuit (IC) (such, as for example, afield-programmable gate array (FPGA) or an application-specific IC(ASIC)), a hard disk, an HDD, a hybrid hard drive (HHD), an opticaldisc, an optical disc drive (ODD), a magneto-optical disc, amagneto-optical drive, a floppy disk, a floppy disk drive (FDD),magnetic tape, a holographic storage medium, a solid-state drive (SSD),a RAM-drive, a SECURE DIGITAL card, a SECURE DIGITAL drive, or anothersuitable computer-readable storage medium or a combination of two ormore of these, where appropriate. Herein, reference to acomputer-readable storage medium excludes any medium that is noteligible for patent protection under 35 U.S.C. §101. Herein, referenceto a computer-readable storage medium excludes transitory forms ofsignal transmission (such as a propagating electrical or electromagneticsignal per se) to the extent that they are not eligible for patentprotection under 35 U.S.C. §101. A computer-readable non-transitorystorage medium may be volatile, non-volatile, or a combination ofvolatile and non-volatile, where appropriate.

This disclosure contemplates one or more computer-readable storage mediaimplementing any suitable storage. In particular embodiments, acomputer-readable storage medium implements one or more portions ofprocessor 902 (such as, for example, one or more internal registers orcaches), one or more portions of memory 904, one or more portions ofstorage 906, or a combination of these, where appropriate. In particularembodiments, a computer-readable storage medium implements RAM or ROM.In particular embodiments, a computer-readable storage medium implementsvolatile or persistent memory. In particular embodiments, one or morecomputer-readable storage media embody software. Herein, reference tosoftware may encompass one or more applications, bytecode, one or morecomputer programs, one or more executables, one or more instructions,logic, machine code, one or more scripts, or source code, and viceversa, where appropriate. In particular embodiments, software includesone or more application programming interfaces (APIs). This disclosurecontemplates any suitable software written or otherwise expressed in anysuitable programming language or combination of programming languages.In particular embodiments, software is expressed as source code orobject code. In particular embodiments, software is expressed in ahigher-level programming language, such as, for example, C, Perl, or asuitable extension thereof. In particular embodiments, software isexpressed in a lower-level programming language, such as assemblylanguage (or machine code). In particular embodiments, software isexpressed in JAVA, C, or C++. In particular embodiments, software isexpressed in Hyper Text Markup Language (HTML), Extensible MarkupLanguage (XML), or other suitable markup language.

Herein, “or” is inclusive and not exclusive, unless expressly indicatedotherwise or indicated otherwise by context. Therefore, herein, “A or B”means “A, B, or both,” unless expressly indicated otherwise or indicatedotherwise by context. Moreover, “and” is both joint and several, unlessexpressly indicated otherwise or indicated otherwise by context.Therefore, herein, “A and B” means “A and B, jointly or severally,”unless expressly indicated otherwise or indicated otherwise by context.

This disclosure encompasses all changes, substitutions, variations,alterations, and modifications to the example embodiments herein that aperson having ordinary skill in the art would comprehend. Similarly,where appropriate, the appended claims encompass all changes,substitutions, variations, alterations, and modifications to the exampleembodiments herein that a person having ordinary skill in the art wouldcomprehend. Moreover, reference in the appended claims to an apparatusor system or a component of an apparatus or system being adapted to,arranged to, capable of, configured to, enabled to, operable to, oroperative to perform a particular function encompasses that apparatus,system, component, whether or not it or that particular function isactivated, turned on, or unlocked, as long as that apparatus, system, orcomponent is so adapted, arranged, capable, configured, enabled,operable, or operative.

What is claimed is:
 1. A method comprising: by a first computing device,determining a communication to be pushed to a second computing deviceassociated with a user of a social network; by the first computingdevice, determining, based on user information stored by the socialnetwork, whether one or more conditions are satisfied for refrainingfrom pushing the communication to the second computing device, wherein:the user information comprises social-networking information stored inrelation to a user node in a social graph associated with the socialnetwork, wherein the user node is associated with the user; and one ormore conditions depend at least in part on a current date and time andone or more events scheduled in a calendar of the user; and if the oneor more conditions are satisfied, then by the first computing device,refraining from pushing the communication to the second computingdevice; else, by the first computing device, sending information to pushthe communication to the second computing device.
 2. The method of claim1, wherein one or more conditions are satisfied when the current dateand time coincides with one or more events scheduled in the calendar ofthe user.
 3. The method of claim 1, wherein the user informationcomprises social-networking information of the user and a currentlocation of the second computing device.
 4. The method of claim 1,wherein the user information comprises social-networking information ofthe user and the second computing device's proximity to one or moreradio-frequency identification (RFID) tags, wherein the RFID tags arecarried by one or more persons or included in one or more objects. 5.The method of claim 1, wherein the user information comprises arelevance score for the communication, and wherein the relevance scoreis based on social-networking information of the user.
 6. The method ofclaim 1, wherein the user information comprises an analysis of thecommunication in conjunction with user-generated content posted to thesocial network.
 7. The method of claim 1, wherein the user informationcomprises a designation of whether the communication is interruptive,and wherein the designation is based on social-networking information ofthe user.
 8. A first system comprising: a memory comprising instructionsexecutable by one or more processors; and the one or more processorscoupled to the memory and operable to execute the instructions, the oneor more processors being operable when executing the instructions to:determine a communication to be pushed to a second system associatedwith a user of a social network; determine, based on user informationstored by the social network, whether one or more conditions aresatisfied for refraining from pushing the communication to the secondsystem, wherein: the user information comprises social-networkinginformation stored in relation to a user node in a social graphassociated with the social network, wherein the user node is associatedwith the user; and one or more conditions depend at least in part on acurrent date and time and one or more events scheduled in a calendar ofthe user; and if the one or more conditions are satisfied, then refrainfrom pushing the communication to the second system; else sendinformation to push the communication to the second system.
 9. The firstsystem of claim 8, wherein one or more conditions are satisfied when thecurrent date and time coincides with one or more events scheduled in thecalendar of the user.
 10. The first system of claim 8, wherein the userinformation comprises social-networking information of the user and acurrent location of the second system.
 11. The first system of claim 8,wherein the user information comprises social-networking information ofthe user and the second system's proximity to one or moreradio-frequency identification (RFID) tags, wherein the REID tags arecarried by one or more persons or included in one or more objects. 12.The first system of claim 8, wherein the user information comprises arelevance score for the communication, and wherein the relevance scoreis based on social-networking information of the user.
 13. One or morecomputer-readable non-transitory storage media embodying softwareoperable when executed by a first computer system to: determine acommunication to be pushed to a second computer system associated with auser of a social network; determine, based on user information stored bythe social network, whether one or more conditions are satisfied forrefraining from pushing the communication to the second computer system,wherein: the user information comprises social-networking informationstored in relation to a user node in a social graph associated with thesocial network, wherein the user node is associated with the user; andone or more conditions depend at least in part on a current date andtime and one or more events scheduled in a calendar of the user; and ifthe one or more conditions are satisfied, then refrain from pushing thecommunication to the second computer system; else send information topush the communication to the second computer system.
 14. The media ofclaim 13, wherein one or more conditions are satisfied when the currentdate and time coincides with one or more events scheduled in thecalendar of the user.
 15. The media of claim 13, wherein the userinformation comprises social-networking information of the user and acurrent location of the second computer system.
 16. The media of claim13, wherein the user information comprises social-networking informationof the user and the second computer system's proximity to one or moreradio-frequency identification (RFID) tags, wherein the RFID tags arecarried by one or more persons or included in one or more objects. 17.The media of claim 13, wherein the user information comprises arelevance score for the communication, and wherein the relevance scoreis based on social-networking information of the user.